scutters

The gameex api can i think already spit your most played tables out as text (json or xml) as well as being able to view them on a webpage, so it probably has that covered as well.

Just a late thought on this, but you can probably get what you want using the gameex online API - GameEx Online, and then view your most played tables from there. (note - you will need to have Gameex online details set up with your details in PinballX settings as well)

@Itchigo from the vpinball.log it looks like you're running the opengl version of VPX (v10.8.0 Beta (Rev. 1975 (051104c), windows OpenGL 64bits) Is there any chance you grabbed the debug version rather than the release version (think that would affect the load times). Suggest trying the non GL (so DX9) release version as that might be a factor in the screenshots / image capture. This one;

It should be pointed at the main PinballX folder - e.g. C:\PinballX not Pinballx/databases/VPX or the pbx recorder folder (C:\Users\Itchiogo-Cab\Desktop\PBXRecorder_x64 as shown in your log) It is but works for image capture too, just deselect the video capture options when you run it and select the image captures you want. That is strange. Are you running VPX 10.8 in fullscreen?, if so that might be the same issue as https://forums.gameex.com/forums/topic/30044-pbx-wont-exit-freezes/ Suggest you leave the system type as visual pinball and change the path for pbxrecorder and see if you can get that to work, then worry about the pbx issue (investigate or change system type back to custom)

@Itchigo Ahh, i think you're using pbx recorder V1.6 as well. Can you try V2.1 from this post - https://forums.gameex.com/forums/topic/28516-pbx-recorder-captures-playfield-backglass-and-dmd-videos-and-images/page/3/#comment-219011

Please attach fresh copies of the pinballx.ini and log.txt files for the new issue. Also, confirm what media do you have in the PinballX\Media\Visual Pinball\Backglass Images and PinballX\Media\Visual Pinball\Backglass Videos folders?

Not sure we're talking about the same thing. I mean changing this setting to Visual Pinball;

Did you enable system #2?, Ini file shows it as disabled. The VPX systems #3 is still not set as a Visual Pinball systemtype as well [System_2] Name=Visual Pinball 9.21 WorkingPath=C:\Visual Pinball TablePath=C:\Visual Pinball\Tables Executable=VPinball921.exe Parameters=/play -"[TABLEPATH]\[TABLEFILE]" Enabled=False SystemType=1 [System_3] Name=VPX WorkingPath=C:\Visual Pinball TablePath=C:\Visual Pinball\VPX Tables Executable=VPinballX.exe Parameters=/play -"[TABLEPATH]\[TABLEFILE]" Enabled=True SystemType=4 The main / inbuilt VP system is enabled though (using VPinball995) What version of VPX are you running (10.7 or 10.8, DX or GL)

I think that's because your VPX system type isn't set as Visual Pinball - change that in PinballX settings and then try. The core(s) maxing out is probably the cause of the longer load times. As far as i'm aware PinballX already lowers it's CPU priority when a game is launched so not much can be done there. The only thing i can suggest is change the VPX launch parameters to -minimized /play -"[TABLEPATH]\[TABLEFILE]" So VP is minimised while launching.. but tbh i can't see that making any more than a miniscule difference. That might be the table script. Check the Table1_Exit routine - does it have a Controller.Stop line?

Bit of an old bugbear of mine which i guess is by design rather than a bug. When exiting a system there seems to be an inbuilt 5 or so seconds delay of black screen before returning to the wheel. This is still present when the 'Enable game exit images' is set to No. When set to Yes the exit image will only appear after the same seconds of delay / black screen. Suggestions, either; If the delay is for safety after closing the 'system' using a Sleep type function to ensure a clean exit completes then remove the game exit images as an option and always show the exit image - but do this before the system is closed to avoid the black screen, then wait for the system to exit before returning to the wheel. Or, remove any sleep / waits from code and instead disable user input for a few seconds (if needed). So the wheel is shown immediately while the system cleanly exits in the background

Sorry, looks like this got buried. Is it still an issue? Assuming it is can you check the event log to see if anything is logged there at the time of the hangs. This might seem a strange suggestion as it's really for VR users but could you also try with the VPXontop app running (https://vpuniverse.com/files/file/15657-vpxontop/) as a test just to see if it helps. Easy enough to remove or disable after. One other thing to try would be running VPX GL non fullscreen, but in windowed mode (under video prefs) with size 1 pixel less then screen width/height - actually, try this first.. i'm fairly hopeful that running VPX non fullscreen will get round issue

Is the table loading normally but just behind PinballX initially (i.e. you can see the DMD running a while before the playfield shows) and is exclusive fullscreen checked in VPX video settings? Edit - if that's not it it's probably worth raising a new issue for the slow loading of tables (not that i have any other ideas if cpu/ram/gpu usage isn't very high either)

Nice You've had a fun week with all that!!

.. or maybe you have vpx set to run as admin? Glad it's sorted anyway Just as a note you probably don't need to create videos and images, the front end will use videos if found first then look for images.

More info from the thread on vpf (https://www.vpforums.org/index.php?showtopic=54204&p=540217) the vpinmame error code is "c0000005" which is a memory access violation. @Itchigo Not sure if that error is on the win7 or win10 (or both?), or if vpinmame is the only app affected. It does hint at deeper trouble which could be software or hardware related. Lots of suggestions in google to try but i'd start with a system file check (sfc /scannow see Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support) and a memory diagnostic check (Diagnose memory problems on your PC (microsoft.com)) as well as running dxdiag. Does that problem relate to the PinballX issue, or even the DP problem?... sorry no idea